Teaching pragmatic model-driven software development
نویسندگان
چکیده
منابع مشابه
Teaching pragmatic model-driven software development
Model-driven software development is surrounded by numerous myths and misunderstandings that hamper its adoption. For long, our students were victims of these myths and considered MDSD impractical and only applied in academy. In this paper we discuss these myths and present our experience with devising an MDSD course that challenges them and motivates students to understand MDSD principles. The...
متن کاملModel-Driven Software Development
Software development is a complex and difficult task that requires the investment of significant resources and carries major risk of failure. According to its proponents, model-driven (MD) software development approaches are improving the way we build software. Model-driven approaches putatively increase developer productivity, decrease the cost (in time and money) of software construction, imp...
متن کاملModel-Driven Software Development
—Model-Driven Software Development œ Techniques and Case Study“ Model-Driven Software Development (MDSD) is an emerging technology approach that has potential to revolutionize the software industry. MDSD has the ability to both increase software delivery velocity, while at the same time reduce complexity and reuse software assets. Experts in the field believe that the MDSD approach helps to abs...
متن کاملSoftMetaWare Model - Driven Software Development
SoftMetaWare is a trademark of SoftMetaWare Ltd. All other trademarks are the property of their respective owners. Included pointers to papers on MDSD Teams and MDSD Activities (process description). Added diagram on MDSD adoption strategy in section Economics of getting from X to MDSD. Updated the Techniques section with further best practices. Included pointers to the paper on Complexity & De...
متن کاملA Pragmatic Approach to Traceability in Model-Driven Development
A common problem in model-driven software development processes is the tracing of requirements across different phases of the software development life cycle and multiple levels of abstraction down to the code level. Because debugging at the model level is not feasible yet, unwanted or unexpected behavior of the executable system needs to be analyzed at the code level at run-time and in a feedb...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Computer Science and Information Systems
سال: 2015
ISSN: 1820-0214,2406-1018
DOI: 10.2298/csis140107022p